home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Varsity Update 1998 August
/
SGI Varsity Update 1998 August.iso
/
docs
/
relnotes
/
pcp
/
ch5.z
/
ch5
Wrap
Text File
|
1998-07-29
|
4KB
|
133 lines
- 1 -
5. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
+o The ``environ'' PMDA for Challenge/Onyx systems has not
yet been ported to the ORIGIN product range.
+o Performance metrics are not reported for SCSI LUNs that
were inactive at the time the Performance Metrics
Collector Daemon ppppmmmmccccdddd(1) was started. The ppppmmmmccccdddd
initialization procedure cannot identify inactive SCSI
LUNs, as found on RAID devices, that may later become
active, in fail-over situations for example. When run
as rrrrooooooootttt, the following will restart ppppmmmmccccdddd and include
the newly active devices:
# /etc/init.d/pcp start
+o Many PCP tools support command line options (----SSSS, ----TTTT, ----OOOO
and ----AAAA) to define a ``time window'' of interest. This
concept is well defined and fully supported when the
source of the performance metrics is an archive. For
real-time sources, the time window specification may be
parsed, but silently ignored, by some tools.
+o There is no SGIHelp for ppppmmmmrrrruuuulllleeeessss(1). Refer to the
reference page, and the _P_C_P _U_s_e_r'_s _a_n_d _A_d_m_i_n_i_s_t_r_a_t_o_r'_s
_G_u_i_d_e.
+o On a PCP collector machine, if there is no network
interface configured to the name of the host (as
returned by hhhhoooossssttttnnnnaaaammmmeeee(1)), then PCP monitor tools trying
to connect to the local ppppmmmmccccdddd(1) will tend to fail, as
they try to use the real host name rather than
_l_o_c_a_l_h_o_s_t to avoid confusion at the user interface.
If this happens, use the command line option
----hhhh llllooooccccaaaallllhhhhoooosssstttt
to force monitor tools to connect to ppppmmmmccccdddd(1) using
_l_o_c_a_l_h_o_s_t.
+o If you have version 1.2 or earlier of the SC4-PCPORA7
product (the ORACLE add-on) and you need to re-install
either the oooorrrraaaacccclllleeee7777 or the oooorrrraaaappppiiiinnnngggg PMDAs, then the
following minor changes will be required to macros in
the Makefiles to ensure the PCP 1.x headers and
libraries are used.
/_v_a_r/_p_c_p/_p_m_d_a_s/_o_r_a_c_l_e_7/_M_a_k_e_f_i_l_e._o_r_a
Change the LLLLDDDDLLLLIIIIBBBBSSSS macro from
LDLIBS = -lpcp -lgen $(PCPLINKOPTS)
to
LDLIBS = /usr/lib/libpcp.so.1 -lgen \
- 2 -
$(PCPLINKOPTS)
If you are creating n32 or n64 binaries then use
/_u_s_r/_l_i_b_3_2 or /_u_s_r/_l_i_b_6_4 in place of /_u_s_r/_l_i_b.
/_v_a_r/_p_c_p/_p_m_d_a_s/_o_r_a_p_i_n_g/_M_a_k_e_f_i_l_e._o_r_a
Change the CCCCFFFFLLLLAAAAGGGGSSSS and LLLLDDDDLLLLIIIIBBBBSSSS macros from
CFLAGS = -$(OBJECT_STYLE) $(ORACFLAGS)
LDLIBS = -lpcp_pmda -lpcp -lgen -lc
to
CFLAGS = -I/usr/include/pcp1.x \
-$(OBJECT_STYLE) $(ORACFLAGS)
LDLIBS = /usr/lib/libpcp_pmda.so.1 \
/usr/lib/libpcp.so.1 -lgen -lc
If you are creating n32 or n64 binaries then use
/_u_s_r/_l_i_b_3_2 or /_u_s_r/_l_i_b_6_4 in place of /_u_s_r/_l_i_b for both
libraries in the LLLLDDDDLLLLIIIIBBBBSSSS macro.